Scholar

Current Lead: @Tibowl & @Reens

Updating the TCL

For any updates, typos, or changes in general, KQM uses GitHub. You can find guides on the sidebar for GitHub onboarding resources.

1. Make edits.
   Scholars make edits on separate branches.

2. Submit Pull Request.

3. Verification & Merge.
   Another scholar can be pinged to check the changes that are submitted and then merges them.

Tickets

1. Opening a ticket.
   An author will open a ticket from #library-submissions.

2. Ticket completion.
   Ticket authors and collaborators should collect evidence and findings, while making a post according to the template. Contributors can be added with /contributor add <username>.

3. Ticket closes.
   Ticket owners can close tickets with /close or with the button at the top of the ticket.

4. Staff verification.
   Staff verifies the ticket and check if the evidence is uploaded to decent storage (like YouTube). Findings should make sense, be understandable, and not be a duplicate that already exists in the TCL. If the finding contradicts existing knowledge, it will need a deeper look.

5. Ticket transcription.
   Once enough scholars verify to reach the threshold, TiBot will automatically make a transcript.

6. Scholar transcription.
   Scholars transcribe the ticket to the TCL, adding the relevant entry onto the page and its evidence page. The automatically generated transcript on the transcription site can be used as a base but should be double checked for context/formatting errors.

7. Submit Pull Request.

8. Verification & Merge.
   Another scholar can be pinged to check the changes that are submitted and then merges them. Once a batch of changes have been made, they can be posted in ⁠#published-tcl and the channels can be /delete'd.

Theoryhunt

1. Request for a theoryhunt.
   A community member or staff member requests for a theoryhunt via ping to Wangsheng Scholar (TC).

2. Posting the theoryhunt.
   Scholars should check for validity of the theoryhunt and ensure that it is not a duplicate. Scholars can use the bot in #theoryhunt to assign the difficulty.

3. Making a ticket.
   Once a community member is interested in the theoryhunt, they can right-click the theoryhunt in order to make a ticket.

   1. If a ticket is made without a right click menu, scholars need to link the theoryhunt functions of the ticket to TiBot. Simply use /convertticket.

4. Continue from Step 4 of Tickets.

5. Ticket closes.
   Ticket owners can close tickets with /close or with the button at the top of the ticket.

6. Staff verification.
   Staff verifies the ticket and check if the evidence is uploaded to decent storage (like YouTube). Findings should make sense, be understandable, and not be a duplicate that already exists in the TCL. If the finding contradicts existing knowledge, it will need a deeper look.

7. Ticket transcription.
   Once scholars verify, TiBot will automatically make a transcript.

8. Scholar transcription.
   Scholars transcribe using the transcript to the TCL, adding the relevant entry onto the page and its evidence page.

9. Submit Pull Request.

10. Verification & Merge.
    Another scholar can be pinged to check the changes that are submitted and then merges them. A batch of changes can be posted in ⁠#published-tcl and the channels can be /delete'd.

Game Updates

TCL

1. Dump assets and update Dim's datamine repo. (See the datamine repo README.md for more details).

2. Run the datamine script.

3. Check changes for unreleased content (such as event weapons, or second half releases) and revert them (namely in the autogenerated images, data and *_icons.json files).

4. Make the PR.

5. A scholar with merge permissions can be pinged to check these changes and merge them.

Discord

1. Make <character>-basic-mechanic channels if needed, list stuff that's needed to be tested in one of first messages and pin it.
   After a while, these channels should die out a bit and can follow tickety stuff step 6-9

2. Convert one of the #<character>-tc> channels that's unused into the new patch's characters.